packages/workspace-server/src/services/claude-cli-sessions/claude-cli-sessions.ts, line 2177-2182 (link)

Files deleted before the DB row is cleared

removeSnapshotFiles runs first, then deleteByTaskId. If anything interrupts execution between those two steps (process crash, unexpected exception after force: true actually succeeds), the import row survives while its files are gone. On the next listForRepo call the source session shows "imported" with a now-deleted importedTaskId, and there is no way to re-import without manually clearing the DB.

Reversing the order — delete the DB row first, then the files — produces better failure semantics: if the file deletion subsequently fails, the source session already shows "new" and can be re-imported; any orphaned file wastes only disk space.

packages/workspace-server/src/services/claude-cli-sessions/claude-cli-sessions.ts, line 2099 (link)

Full-file read in importSession vs chunked reads in the listing path

fs.readFile(sourcePath, "utf-8") loads the entire transcript into a JavaScript string before any processing, while listForRepo deliberately uses bounded head/tail reads. A CLI session with thousands of turns can easily be several megabytes; this import call then allocates a second copy while building the rewritten array. Using readline (or createReadStream) would keep memory usage proportional to a single line at a time and is consistent with the chunked approach already used in scanning.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!